Systems and methods for configuring and operating a wireless control system in a vehicle for activation of a remote device

ABSTRACT

Control systems for mounting in a vehicle and for transmitting a signal to a receiver associated with a device for opening or closing a movable barrier when the receiver receives an authorized signal are provided.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/344,082, filed Dec. 24, 2008, now U.S. Pat. No. 8,311,490,incorporated herein by reference in its entirety.

BACKGROUND

The present disclosure generally relates to systems and methods forconfiguring a wireless control system of a vehicle.

Wireless control systems are provided in vehicles for activities such asactuating a remote device (e.g., a garage door opener), establishing adata communication link with a remote system, establishing a voicecommunication link with a portable electronic device, and for otherpurposes.

Vehicle-based wireless control systems are sometimes difficult toconfigure for use with particular remote devices, systems, and/orportable electronic devices.

Improved systems and methods for configuring a wireless control systemof a vehicle are needed.

SUMMARY

One embodiment relates to a control system for mounting in a vehicle andfor transmitting a signal to a receiver associated with a device foropening or closing a movable barrier when the receiver receives anauthorized signal. The control system includes a transmitter and memorystoring a first set of messages for including with transmissions to thereceiver from the transmitter. The control system further includes aninterface configured to receive a second set of messages from at leastone of a portable electronic device and a remote system, wherein thesecond set of messages comprises a plurality of messages. The controlsystem further includes a circuit configured to provide the second setof messages to the memory for storage. The control system yet furtherincludes a user input interface configured to receive an indication ofuser input from a user interface element and to provide the indicationto the circuit. The circuit may be configured to provide at least one ofthe messages stored in memory to the transmitter for transmission to thereceiver based on the indication received from the user input interface.The control system may include a receiver for receiving a signal from anoriginal portable transmitter pre-configured to send an authorizedsignal to the receiver. The circuit may be configured to identify acharacteristic associated with the received signal and to use the countto select which of the messages stored in memory to provide to thetransmitter when the indication is received from the user inputinterface. The circuit may include memory and a processor, the memoryhaving computer code for execution by the processor and forreprogramming logic of the circuit based on update information receivedfrom the interface. The signals and the messages can be rolling codemessages, fixed code messages, or any other types of messages.

Another embodiment relates to a control system for mounting in a vehicleand for transmitting a signal to a receiver associated with a device foropening or closing a movable barrier when the receiver receives anauthorized signal. The control system includes an interface configuredto exchangeably receive different transmitters. The control systemfurther includes a power supply configured to supply power to theinterface. The control system yet further includes a user inputinterface configured to receive user input from a user interfaceelement. The control system also includes a circuit communicablycoupling the user input interface and the interface for receiving atransmitter. The circuit is configured to utilize different transmittersreceived by the interface so that common user input received at the userinput interface results in like behavior by the different transmitters.

Another embodiment relates to a control system for mounting in a vehicleand for transmitting a signal to a receiver associated with a device foropening or closing a movable barrier when the receiver receives anauthorized signal. The control system includes a transmitter and memorystoring a plurality of identifiers, each identifier associated with adifferent possible receiver manufacturer, each different possible remotecontrol system manufacturer associated with at least one message, analgorithm for generating a message, or at least one message and analgorithm for generating a message. The control system further includesan interface for receiving an identifier and a control circuitconfigured to compare the received identifier to one or more of theplurality of identifiers stored in memory and to cause the transmitterto transmit, based on the comparison, at least one message associatedwith the manufacturer based on the at least one message stored inmemory, the algorithm for generating a message, or the at least onemessage and the algorithm for generating the message. The controlcircuit may be configured to transmit a plurality of messages associatedwith the manufacturer indicated by the received identifier during aprocess of training the control system to send authenticatedtransmissions to the receiver.

Another embodiment relates to a control system for mounting in a vehicleand for transmitting a signal to a receiving device associated with adevice for opening or closing a movable barrier when the receivingdevice receives an authorized signal, the receiving device associatedwith an original transmitter. The control system includes a controlcircuit and a receiver communicably coupled to the control circuit andconfigured to receive a first signal from the original transmitter. Thecontrol system further includes memory storing a plurality ofidentifiers, each identifier associated with a different possiblealgorithm, wherein the first signal comprises an identifier. The controlcircuit is configured to detect the identifier of the first signal andto use the detected identifier of the first signal and the plurality ofidentifiers stored in memory to determine which of a plurality ofpossible algorithms to utilize in order to complete a successfultraining process with the receiver. The control circuit is furtherconfigured to complete the analysis of the first signal without decodinga data portion of the first signal that is used by the receiving devicefor authentication.

Another embodiment relates to a control system for mounting in a vehicleand for transmitting a signal to a receiver associated with a device foropening or closing a movable barrier when the receiving device receivesan authorized signal, the receiving device associated with an originaltransmitter. The control system includes a receiver configured toreceive and recognize a discrete identifier message from the originaltransmitter before or after a data message. The control system furtherincludes a circuit configured to be provided the discrete identifiermessage and configured to analyze the discrete identifier message todetermine a manufacturer of the remote control system. The controlsystem yet further includes an input from a user interface for receivinga command to transmit a control signal to the receiving device. Thecontrol system may further include a transmitter for transmittingcontrol signals to the receiving device. The circuit is configured tocause the transmitter to transmit a first control signal based on themanufacturer in response to a first command received at the input. Thecircuit is further configured to cause the transmitter to transmit asecond control signal based on the manufacturer in response to a secondcommand received at the input. The circuit is yet further configured toreceive an indication from the user at the input to indicate whether thefirst control signal or the second control signal caused the device foropening or closing a movable barrier to respond. The circuit configuresitself for future transmissions to the receiving device based on thereceived indication.

Another embodiment relates to a control system for mounting in a vehicleand for transmitting a signal to a receiver associated with a device foropening or closing a movable barrier when the receiver receives anauthorized signal. The control system includes a transmitter and memorystoring a plurality of codes, a first group of the codes compatible withold receiver standards and a second group of the codes associated withnew receiver standards. The control system further includes an inputconfigured to receiving a command from a user interface element. Thecontrol system yet further includes a circuit configured to cause thetransmitter to transmit the first group of codes followed by the secondgroup of codes when the command is received at the input.

Alternative exemplary embodiments relate to other features andcombinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE FIGURES

The disclosure will become more fully understood from the followingdetailed description, taken in conjunction with the accompanyingfigures, wherein like reference numerals refer to like elements, inwhich:

FIG. 1 is a perspective view of a vehicle having a control systemconfigured to provide a control signal to a remote device such as agarage door opener, according to an exemplary embodiment;

FIG. 2 is a block diagram of a system such as that illustrated in FIG.1, according to an exemplary embodiment;

FIG. 3A is a block diagram of an original portable transmittercommunicating an identifier message and a data message to a vehiclecontrol system and remote device for training purposes, according to anexemplary embodiment;

FIG. 3B is a flow chart of a process for configuring a vehicle controlsystem for authenticated transmissions to a remote device using anidentifier message transmitted from an original transmitter, accordingto an exemplary embodiment;

FIG. 3C is a flow chart of a process for configuring a vehicle controlsystem for authenticated transmissions to a remote device by analyzing acontrol signal transmitted from an original transmitter, according to anexemplary embodiment;

FIG. 3D is a flow chart of a process for training a vehicle controlsystem based on a determined manufacturer, according to an exemplaryembodiment;

FIG. 3E is a flow chart of a process for training a vehicle controlsystem based on user input regarding receiver information, according toan exemplary embodiment;

FIG. 4A is a flow chart of a process for training a vehicle controlsystem and a remote device for communications using a format differentfrom that associated with an original transmitter for the remote device,according to an exemplary embodiment;

FIG. 4B is a flow chart of a process for configuring a receiverassociated with a remote device to receive authenticated transmissionsfrom a vehicle control system having a transmission format differentthan that associated with an original transmitter for the remote device,according to an exemplary embodiment;

FIG. 4C is a flow chart of a process for training a vehicle controlsystem to communicate with a receiver configured to receive two types ofcontrol signals, according to an exemplary embodiment;

FIG. 5 is a block diagram of a vehicle control system configured toreceive information from a plurality of devices, the information for usein training the vehicle control system for use with a remote device,according to an exemplary embodiment;

FIG. 6 is a block diagram of a vehicle control system coupled to a homenetwork and remote device, the vehicle control system configured to useinformation received from the home network in a training routine,according to an exemplary embodiment;

FIG. 7 is a block diagram of an original transmitter and a vehiclecontrol system, the vehicle control system configured to receiveinformation from the original transmitter for use in training, accordingto an exemplary embodiment;

FIG. 8 is a block diagram of an original transmitter and a vehiclecontrol system, the vehicle control system configured to be commanded bya key fob during a training process, according to an exemplaryembodiment;

FIG. 9 is a flow chart of a process for training a vehicle controlsystem and a receiver of a remote device for authenticatedcommunications, the vehicle control system being configured to transmita different set of codes for a different training window of thereceiver, according to an exemplary embodiment;

FIG. 10 is a flow chart of a process for transmitting messages from avehicle control system to a remote device during a training procedure,the messages being condensed, according to an exemplary embodiment;

FIG. 11 is a flow chart of a process for training a vehicle controlsystem based on user input received during a training procedure,according to an exemplary embodiment;

FIG. 12 is a flow chart of a process for training a vehicle controlsystem for communications to a receiver, the codes transmitted to thereceiver for training purposes having a sort order to compensate fordiffering receiver learn window lengths, according to an exemplaryembodiment; and

FIG. 13 is a flow chart of a process for using a vehicle control systemto request a longer learning window from a receiver via a wirelesstransmission, according to an exemplary embodiment.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

Before turning to the figures, which illustrate the exemplaryembodiments in detail, it should be understood that the application isnot limited to the details or methodology set forth in the descriptionor illustrated in the figures. It should also be understood that theterminology is for the purpose of description only and should not beregarded as limiting.

Referring generally to the figures, systems and methods for configuringand operating a wireless control system mounted in a vehicle foractivation of a remote device are shown and described.

Referring now to FIG. 1, a perspective view of a vehicle 100 having acontrol system 102 configured to provide a control signal (e.g., aformatted radio frequency signal) to a remote device 104 is shown,according to an exemplary embodiment. According to the embodiment shownFIG. 1, remote device 104 is a garage door opener for opening a garagedoor such as the garage door illustrated in FIG. 1. Remote device 104includes or is associated with a receiver 105 that receives the controlsignal and causes (e.g., via one or more signals) the garage door openerto open the garage door based on the received control signal. A receiverincluded or associated with a remote device such as garage door openerare typically configured to cause the remote device to actuate or changestates only if the control signal is determined to be from an authorizeddevice. The receiver typically determines whether or not the controlsignal is from an authorized device based on characteristics of thecontrol signal. For example, a receiver included or associated with theremote devices may be configured to cause the remote device to actuateor change state if the control signal is sent at a certain frequency orfrequencies, includes representations of particular codes, is formattedin a particular way, includes a certain cryptography key, is modulated acertain way, and the like.

A receiver such as receiver 105 included or associated with a remotedevice such as remote device 104 is typically associated with one ormore original portable transmitters such as portable transmitter 106configured to provide an appropriately formatted control signal to thereceiver. Portable transmitter 106 may be an original transmitter soldwith remote device 104 and/or previously configured for communicationswith receiver 105 of remote device 104. Control system 102 mounted invehicle 100 may not be pre-configured for communications with the user'sparticular remote device 104 when first sold to a user (with vehicle 100or otherwise). Vehicle control system 102 can be configured for wirelesscommunications with remote device 104 via a one or more configurationprocesses (e.g., training processes, setup processes, etc.). Forexample, control system 102 can include a radio frequency receiverconfigured to receive radio frequency control signals from portabletransmitter 106 and to configure itself using the received radiofrequency control signals. According to other exemplary embodiments,control system 102 can include a plurality of stored codes fortransmitting with control signals and for actuating a plurality ofdifferent types of remote devices such as garage door openers. Atraining process of this type of system may rely on the control systemtransmitting the plurality of stored codes in a sequence to the remotedevice, the user indicating when he or she observes the remote devicechange states to the vehicle control system; the vehicle control systemconfiguring itself based the timing of the indication (e.g., storing oneor more codes associated with the timing of the indication).

Referring now to FIG. 2, a block diagram of the system illustrated inFIG. 1 is shown, according to an exemplary embodiment. Original portabletransmitter 106 is shown to include control circuitry 110, transmitter205, UI element 206, and memory 203. Receiver 207 of control system 102may be configured to receive information from original portabletransmitter 106 via RF communications. Using the received information,control system 102 can configure itself for authenticated transmissionsfrom the control system 102's transmitter 202 to remote device 104'sreceiver 105. According to various exemplary embodiments, vehiclecontrol system 102 can configure itself without reliance on informationreceived from original portable transmitter 106 via a “guess and test”training method (e.g., the vehicle control signal tests for anauthenticated control signal by transmitting a plurality of controlsignals to the remote device).

Control circuitry 110 of original portable transmitter 106 may generallybe configured to format a control signal for transmission to remotedevice 104 via transmitter 205 or to cause transmitter 205 to format andsend the control signal. Control circuitry 110 is shown to includememory 203 for storing information such as information regarding thecontrol signal or remote device 104. Control circuitry 110 furtherincludes UI elements 206 (e.g., buttons, switches, touch-sensitiveelements, voice recognition systems, touch screens, etc.) which may bepressed or otherwise used by a user of original portable transmitter 106to transmit information.

Control system 102 is shown to include transmitter 202 (e.g., a radiofrequency (RF) transmitter), I/O circuit 208, UI circuit 210, andprocessing circuit 212. According to an exemplary embodiment, controlsystem 102 is configured to be mounted to a vehicle such as vehicle 100(e.g., mounted in a vehicle interior location, a center stack location,a dashboard location, a center console, an overhead console, a floorconsole, an instrument panel, a door panel, a visor, a rear-view mirror,a headliner location, in multiple vehicle locations, etc.).

According to an exemplary embodiment, control system 102 may transmit acontrol signal to receiver 105 of remote device 104 based on user inputsignals received from user interface (UI) 224 at UI circuit 210. Forexample, when one or more of a plurality of UI elements 226 are pressedor otherwise used. UI circuit 210 and processing circuit 212 may causeRF transmitter 202 to transmit a control signal associated with thepressed or activated UI element 226. The transmission of the controlsignal can also be triggered based on input received from other vehiclesystems 222 via I/O circuit 208. Other vehicle systems 222 may include,for example, a positioning device (e.g., GPS receiver) configured tocause RF transmitter 202 to transmit the control signal based onposition information received at I/O circuit 208. Other vehicle systems222 may also include vehicle communications systems (e.g., configured toreceive data from a mobile phone, an Internet source, or otherwise),vehicle center stack control systems, voice recognition systems, bodyelectronics modules configured to receive signals from key fobs or otherremote controls, and the like that may be configured to provide signalsthat control or otherwise affect the behavior of control system 102.

Processing circuit 212 is shown to include memory 214 and processor 216.Processing circuit 212 may be configured to initiate and control thetransmission of a control signal by controlling and/or providinginformation to transmitter 202. When information is received by acircuit 208 or 210, processing circuit 212 may be configured to storethe received information in memory, to process the received informationusing processor 216, and/or to set variables stored in memory 214.Control system 102 is further shown to include a power supply 228 forsupplying a power source to control system 102.

Processing circuit 212 and/or processor 216 may be or include one ormore integrated circuits, application specific integrated circuits,general purpose processors, memory chips, logic gates, fieldprogrammable gate arrays, and/or other electronics components forprocessing user input, received data communications, and receivedcontrol signals from other components attached to processing circuit 212and/or processor 216. Memory 214 may be any type of memory device, maybe local to processing circuit 212 (as shown), remote from processingcircuit 212, or otherwise communicably coupled to processing circuit212. Memory 214 can be or include random access memory, read onlymemory, and/or any other type of memory. Memory 214 can be configured tostore codes for communication to various types of remote devices,algorithms for generating codes or control signals for various types ofremote devices, variables for storing system or user set values,variables for storing pointers to codes to be used, constant values,transmission schemes, temporary values, receptions from an originaltransmitter, computer code for execution by processor 216 for executingthe various processes described herein or supporting functions, or thelike.

Remote device 104 generally includes a receiver 105 for receivinginformation regarding the use of remote device 104. For example,receiver 105 may be configured to receive a control signal commandingremote device 104 to perform an activity such as opening a garage door.Receiver 105 can be configured to receive a narrow band of frequencies,a wide band of frequencies, communications centered around one or morefrequencies, or any type of radio frequency receiver configured toreceive communications from original portable transmitter 106 and/orvehicle control system 102. According to an exemplary embodiment,receiver 105 is configured to receive radio frequency communications ataround 285-450 Mhz. Receiver 105 may also be configured to process thesignals received to determine if the signals are from an authorizedsource or otherwise expected. For example, receiver 105 may decode ordemodulate received transmissions or check decode or demodulatetransmissions against a cryptographic algorithm, against a checksum,against a stored value, against a count, or against any other criteria.

Use of an Identifier Message for Vehicle Control System Configuration

As new remote devices are developed, the memory device and/or processingcircuit of the vehicle control system may not include logic forreceiving, decoding, and training to regular transmissions of originalportable transmitters for the new remote devices. According to variousexemplary embodiments, however, the vehicle control system may beconfigured to identify a characteristic such as the manufacturer of theremote device or original portable transmitter and to generatetransmissions that may be recognized and authenticated by the remotedevice based on the identified characteristic.

Referring now to FIG. 3A, a block diagram of original portabletransmitter 106 communicating with vehicle control system 102 and remotedevice 104 is shown, according to an exemplary embodiment. Some datamessages transmitted for authentication to remote device 104 aredifficult for devices such as vehicle control system 102 to interpret(e.g., decode, decrypt, etc.). Original portable transmitter 106 shownin FIG. 3A may be configured to transmit an identifier messageseparately from a data message (e.g., an encrypted data message, anencoded data message, etc.). The identifier message may be used byvehicle control system 102 for training purposes while the data messagemay be used by remote device 104 to actuate remote device 104 (e.g., toopen the garage door) and/or to set remote device 104 into a trainingmode (e.g., a mode whereby vehicle control system 102 or another devicecan train to remote device 104 for a period of time).

Referring now to FIG. 3B, a flow chart of a process 300 for configuringa vehicle control system for authenticated transmissions to a remotedevice is shown, according to an exemplary embodiment. Process 300 isshown to include the original portable transmitter transmitting anidentifier message (e.g., a discrete identifier message, an identifiermessage mixed or combined with other information, etc.) before or aftertransmitting a data message (step 302). The vehicle control systemreceives the identifier message (step 304) and configures itself basedon the received identifier message (step 306). The data message may be amessage pre-programmed for authenticated reception by the remote device.The identifier message may be configured to allow a receiver to identifya manufacturer, a model number, a transmission scheme, or any number ofcharacteristics regarding the remote control system. According to anexemplary embodiment, the identifier message may be a three bit binaryidentifier interpretable by the vehicle control system (e.g., thevehicle control system stores a lookup table of the identifiers inmemory, the lookup table associating the possible identifiers with atleast one characteristic that can be used during a training process).Different formats or identifier lengths may be transmitted by theoriginal transmitter and interpreted by the vehicle control system.According to various exemplary embodiments, if the vehicle controlsystem is configured with many different codes for many differentpossible remote devices, upon receiving an identifier message thatindicates the remote control system is from brand x, the vehicle controlsystem can configure itself to only transmit brand x codes during atraining procedure, or during normal operation. In some embodiments,“normal operation” means user-requested transmissions from the vehiclecontrol system to the remote device after the vehicle control system hasbeen trained to the remote device.

While the vehicle control system may configure itself in a number ofdifferent ways based on the received identifier message in step 306, oneexemplary configuration process is illustrated in FIG. 3B. As mentionedabove, as new remote devices are released by manufacturers, theauthentication processes (e.g., and accompanying codes that may beauthenticated by the remote devices) may be updated for a number ofreasons. While the manufacturer of the remote device may prefer that thenew authentication processes be used, the remote devices may beconfigured to authenticate legacy codes (e.g., old codes andauthentication schemes associated with the manufacturer) in addition tonew codes. Accordingly, when the vehicle control system receives anidentifier message and processes the identifier message to determine amanufacturer of the remote device, the vehicle control system canconfigure itself to transmit legacy control signals to the remote device(step 308). For example, the vehicle control system can configure itselfto transmit one or more legacy control signals to the remote device withthe next button press. According to some training processes, a buttonmust be pushed on the receiver (step 310) associated with the remotedevice to enter the receiver into a training mode (e.g., a learn mode)so that the remote device can configure itself to authenticate messagesreceived from the vehicle control system. The vehicle control system canthen receive user input (e.g., a button press, a voice command, etc.) totransmit a control signal to the remote device—and, due to theconfiguration of step 308, may transmit a legacy control signal to theremote device (step 312). Upon reception of the legacy control signal,the receiver may train to the legacy control signal (e.g., configureitself to accept future control signals similarly formatted from thevehicle control system). The vehicle control system can configure itselfto associate the legacy control signal with a user input element (e.g.,a button) or a command (e.g., a voice command of “open home garagedoor”) for normal use.

Determining Basic Information for Training by Analyzing an OtherwiseUnrecognized Control Signal from the Original Portable Transmitter

In some cases, the original portable transmitter may not be configuredto transmit a discrete identification message that the vehicle controlsystem can use to identify the manufacturer or other importantcharacteristics of the remote device. According to the embodimentdescribed in FIG. 3C, the vehicle control system is configured toprocess and/or test any received message(s) from the original portabletransmitter to identify the manufacturer or other importantcharacteristics of the remote device. Process 320 includes the originalportable transmitter transmitting a message and the vehicle controlsystem attempting to learn and/or identify the message (step 322). Ifthe vehicle control system determines that it cannot train to themessage or otherwise recognize the message (step 324) the vehiclecontrol system can be configured to at least process the message todetermine the manufacturer (step 326). The vehicle control system canthen configure itself to transmit one or more legacy control signalsassociated with the determined manufacturer (step 328). The vehiclecontrol system can be configured to determine the manufacturer in step326 in a number of different ways. For example, the vehicle controlsystem can make a determination based on the frequency of the signalreceived from the original transmitter, a length of the signal, apattern of the signal, or otherwise.

Training to a Remote Device Manufacturer Having Multiple AuthenticationAlgorithms or Code Formats

Sometimes multiple types of control signal formats, code types,frequencies, or the like may be associated with one manufacturer.According to the exemplary embodiment of FIG. 3D, the vehicle controlsystem is configured to receive an identifier message (step 344)transmitted from the original portable transmitter before or after adata message (step 342). The vehicle control system processes theidentifier message to determine the manufacturer (step 346). Accordingto various alternative embodiments, the manufacturer may be determinedvia any number of ways rather than based on the receipt of an identifiermessage. For example, a vehicle control system may be configured todetermine the manufacturer based on the control signal format, a codepattern, a frequency band, a frequency center, or the like. Upondetermining the manufacturer (e.g., using fuzzy logic, making adetermination with a certain level of confidence, etc.) the vehiclecontrol system may configure itself so that transmissions commanded bythe user are in accordance with codes associated with the manufacturer.When the vehicle control system receives first user input (step 348) thevehicle control system may transmit a first control signal based on themanufacturer and in response to the first user input (step 350). Whenthe vehicle control system receives second user input (step 352) thevehicle control system may transmit a second control signal based on themanufacturer and in response to the second user input (step 354).According to an exemplary embodiment, the first control signal and thesecond control signal are associated with different models (e.g., afixed code model and a rolling code model, an old model and a new model,a legacy model, a model having a first decryption algorithm, a modelhaving a second decryption algorithm, a model configured to accepttransmissions at a first frequency, a model configured to accepttransmissions at a second frequency, etc.) produced by the determinedmanufacturer. According to an exemplary embodiment, a plurality ofmessages associated with the determined manufacturer may be transmittedwith each button press in an attempt to find a control signal that isproperly authenticated by the remote device. According to otherexemplary embodiments, the user interface activity that causes the firstand the second different control signals associated with themanufacturer to transmit can be based on holding a button, providing avoice command, providing touch screen input or any other user inputactivity.

Vehicle Control System Selection of Control Signal Format Based on UserInput Regarding the Remote Device's Receiver

Referring now to FIG. 3E, a flow chart of a process 360 for training avehicle control system based on user input regarding receiverinformation is shown, according to an exemplary embodiment. Process 360is shown to include prompting a user for manufacturer or other receiverinformation (step 362) and receiving corresponding input from the user(step 364). The vehicle control system can then be configured totransmit a plurality of control signals that could be compatible withthe receiver based on the received input (step 366).

Configuration of Vehicle Control System for Authenticated Communicationwith Remote Device without Use of the Communication Scheme Used by theOriginal Portable Transmitter

Practical, technical, and user-driven difficulties can make processesfor training to information received from an original transmitterchallenging. Similarly, in systems that use a “guess and test” typetraining method wherein an original transmitter is not used, thetraining process can be challenging and/or result in the vehicle controlsystem being trained to a less than optimal control signal. According tovarious exemplary embodiments described herein, the vehicle controlsystem (e.g., such as that shown in FIG. 2) can be configured totransmit a signal that is unlike or unrelated to the control signalnormally sent to a remote device from the device's original transmitter.According to various exemplary embodiments, for example, the processingcircuit of the vehicle control system can be configured to cause thevehicle control system's transmitter to transmit a control signalaccording to a format or protocol unrelated to the original transmitter;the remote device's receiver being configured to receive andauthenticate transmissions according to both the format of the originaltransmitter and the format of the vehicle control system.

Referring now to FIG. 4A, a flow chart of a process 400 for training avehicle control system to a remote device is shown, according to anexemplary embodiment. Process 400 includes receiving a message from anoriginal portable transmitter at a certain frequency (step 402). Thevehicle control signal may then attempt to recognize the message (step404) (e.g., recognize the manufacturer of a remote device associatedwith the message, recognize the format of the message, recognize theencryption scheme of the message, recognize the rolling code countassociated with the message, etc.). Process 400 also includes, upon thevehicle control system failing to recognize the message, generating acontrol signal associated with the vehicle control system and at thefrequency (step 406). For example, according to an exemplary embodimentthe vehicle control system is configured to transmit its own type ofcontrol signal. The remote device receiver is configured to receive bothcontrol signals according to its default format as well as a formatassociated with the vehicle control system (e.g., associated with thevehicle control system brand, etc.). Once the remote device receives thegenerated control signal it can store information regarding the controlsignal for future recognition (step 408).

Referring now to FIG. 4B, a flow chart of a process 420 for configuringa receiver of a remote device (e.g., a receiver associated with a garagedoor opener) is shown, according to an exemplary embodiment. Process 420is shown to include configuring the remote device receiver to respond tocontrol signals particular to the remote device receiver or itsmanufacturer (step 422) and configuring the remote device receiver torespond to control signals particular to a second type of control signal(step 424). The second type of control signal may be a vehicle controlsignal compatible with a type, kind, or brand of vehicle control systemor universal transmitter (e.g., a type of control signal compatible withJohnson Controls HomeLink® brand of universal transmitters). Configuringsteps 422, 424 may be conducted by the receiver's manufacturer, by aninstallation technician, or otherwise. Once configured and the receiveris installed, a vehicle control system can train to the receiver and thereceiver can train to the vehicle control system. The training processmay include receiving a first control signal particular to the remotedevice receiver and previously recognized (step 426). Step 426 mayinclude, for example, receiving a first control signal from an originalportable transmitter where the rolling code count received with thecontrol signal at the remote device receiver is expected. The receivermay be configured to open a training window (e.g., enter a training modefor a period of time) after authenticated reception of the first controlsignal (step 428). When the training window is open (e.g., the receiveris in a training mode of operation), the receiver can be configured totrain to a second control signal (step 432) after the second controlsignal is received (step 430). The second control signal can be of adifferent format than that received from the original portabletransmitter in step 426. According to an exemplary embodiment, thesecond control signal is of a format compatible with the vehicle controlsystem manufacturer. According to various alternative embodiments, auser interface associated with the receiver or the remote device may beused to configure the remote device for receiving the second type ofcontrol signal from the vehicle control system. For example, accordingto some exemplary embodiments a button or a series of buttons on agarage door opener may be pressed to set the receiver into a train modecompatible with the second control signal type. According to yet otherexemplary embodiments, the receiver may be configured to accept a memorycard, an update via a wired or wireless interface, or otherwise capableof receiving updates or commanded configuration changes so that thereceiver can recognize, accept, and be trained to the second type ofcontrol signal.

Referring now to FIG. 4C, a flow chart of a process 440 for training avehicle control system to a receiver configured to receive two types ofcontrol signals as specified, for example, in FIG. 4B is shown,according to an exemplary embodiment. Process 440 is shown to includepressing a button on the original transmitter to cause transmission of afirst control signal in accordance with a first format (step 442). Thefirst format may be a format pre-configured to be compatible with thereceiver. When user input is received at the vehicle control system(step 444) the vehicle control system can send a control signal inaccordance with a standard associated with the vehicle control systemand not in accordance with the first format (step 446). The vehiclecontrol system may be configured to complete the training process withthe remote device receiver using the control signal format of thevehicle control system (step 448).

Systems and Methods for Updating a Vehicle Control System forCompatibility with New or Updated Remote Devices

Referring now to FIG. 5, a block diagram of a vehicle control system 500and various other interfacing devices are shown, according to anexemplary embodiment. Vehicle control system 500 is shown to include avariety of interfaces and communications hardware for receivinginformation for updating a new or updated remote device. One or more ofthese interfaces or communications hardware parts may be provided to anyone vehicle control system and it should be appreciated that a vehiclecontrol system capable of updating need not include each of theillustrated interfaces.

Vehicle control system 500 is shown to include processing circuit 512having memory 514 and processor 516. Processing circuit 512 is generallyconfigured to process the update information received via one or more ofthe interfaces or communications hardware of vehicle control system 500.For example, when new codes or a new algorithm for authenticatedreception by remote device 504's receiver 506 are received, processingcircuit 512 can properly update the operational algorithm for thevehicle control system based on the received updates. If the updates arenew codes, then processing circuit 512 may extract the new codes andupdate its memory 514 or a memory associated with transmitter 502 withthe new codes for transmission to receiver 506. Power supply 528 can beconfigured to supply power to vehicle control system 500 and/or to oneor more of the coupled devices (e.g., if the devices are coupled via awired connection).

According to an exemplary embodiment, user input received at UI circuit510 from UI 524 and/or UI elements 526 may be received and used toconfigure the vehicle control system. The user input may indicate, forexample, the manufacturer of remote device 504, a passkey for remotedevice 504, a model number for remote device 504, a serial number forremote device 504, an algorithm identifier for remote device 504, acount for remote device 504, or any other piece of information regardingremote device 504. The user input may be used directly by processingcircuit 512 to configure vehicle control system 500 and/or transmitter502. According to various other exemplary embodiments, processingcircuit 512 may use the received user input to initiate an activityinvolving one or more of the interfaces to external devices. Forexample, if a model number or an algorithm identifier is input by a userregarding an unrecognized remote device, processing circuit 512 mayinclude logic that determines an update should be searched for,requested, and/or received from an external device. Processing circuit512 may request information in a way that is transparent to the user ofthe vehicle control system, or processing circuit 512 may prompt theuser for further input, the connection of an external device,information for connecting to a remote server 509, or other informationvia UI 524 or otherwise.

Remote server 509 can be a server storing rolling codes, algorithms,crypt keys, or other information that processing circuit 512 can use toconfigure vehicle control system 500. Remote server 509 can be a sourcewhich is directly connected to via receiver 507 or remote server 509 canbe a source which is connected to a network to which receiver 507 candirectly or indirectly connect. For example, remote server 509 can be aninternet server and receiver 507 may be configured to connect to theinternet via a mobile phone provider. Processing circuit 512 can causereceiver 507 to request information for updating vehicle control system500 from remote server 509. Processing circuit 512 can also beconfigured to be provided the received information from receiver 507 andto use the received information to complete the configuration of vehiclecontrol system 500.

Audio input and speech recognition electronics 530 can be configured toallow a user in the vehicle to speak commands (e.g., requests,utterances, etc.) that are received at audio input device 532 (e.g., amicrophone mounted in the vehicle) and to process the commands.Representations of the commands can be provided from audio input andspeech recognition electronics 530 to processing circuit 512. Processingcircuit 512 may be configured to allow a user to command updates, enterinformation (e.g., passkey information, manufacturer information, codeinformation, serial number information) regarding remote device 504using audio input and speech recognition electronics 530.

Other vehicle systems 522 may also be communicably coupled to vehiclecontrol system 500 via I/O circuit 508 another interface, or otherwise.Other vehicle control systems 522 may be or include any user interfacesystems (e.g., a touch screen system, steering wheel mounted controls,overhead console controls, a connection to a mobile phone, a connectionto a portable electronic device brought within the vehicle, a vehiclemounted hands-free communication system, a vehicle data bus system, aremote keyless entry system, a tire pressure monitoring system, avehicle computer, a vehicle entertainment system, etc.). In someembodiments, vehicle control system 500 may be controlled by one or moreof the other vehicle systems (e.g., if the other vehicle system is theprimary user interface controller for the vehicle). In some embodiments(e.g., where vehicle control system 500 is a relatively stand-alone areduced function control system for training for authenticatedtransmissions to a remote device (e.g., garage door opener)), vehiclecontrol system 500 may only access information and/or receiveinformation from the other vehicle control systems. In yet otherembodiments, vehicle control system 500 may be the primary userinterface controller for the vehicle and/or communications controllerfor the vehicle and may be used to control the other vehicle systems522.

USB interface 534 may be included with vehicle control system 500 forreceiving code information from one or more devices 538 also having aUSB interface. According to an exemplary embodiment, an originaltransmitter 536 could be programmed to include one or more codes,identifiers, counts, algorithms or other information which can betransmitted to vehicle control system 500 via USB interface 534. Forexample, original transmitter 536 may be supplied with the garage dooropener and include a unique code for opening the particular garage dooropener with which it is sold.

For security reasons the garage door opener may only be able torecognize two of the same code—one for the original transmitter and onefor another device. The original transmitter may be configured to managea token or other identifier which it can only provide to one otherdevice at a time. A universal transmitter such as vehicle control system500 may be given the token (e.g., the original transmitter stores aunique identifier of the vehicle control system and transmits the uniqueidentifier to the remote device 504 so that the remote device willauthenticate transmissions from vehicle control system 500) when pluggedinto USB interface 534 and also given a code or codes and/or analgorithm for communicating with remote device 504. When originaltransmitter 536 is plugged into a different device (e.g., a differentvehicle control system) original portable transmitter 536 may learn thatsystem's identifier and communicate the identifier to remote device 504so that the new system and remote device 504 can train. Remote device504 will no longer accept the vehicle control system 500's transmissionsand may now accept the new system's transmissions.

According to an exemplary embodiment, USB device 538 can be a “thumbdrive” or another memory device (e.g., a hard drive, a flash drive, amemory card reader, etc.) configured to read and/or write informationstored thereon to and/or from USB interface 534. The thumb drive may bemailed or otherwise provided to a user of a remote garage door openerfor programming devices such as vehicle control system 500 for operationwith the garage door Opener. The thumb drive may store one or many codes(e.g., tens, hundreds, thousands) that the vehicle control system mayuse to communicate with remote device 504. When plugged into orotherwise connected to USB interface 534, the thumb drive can transferall or a portion of the codes to memory 514 as controlled by processingcircuit 512. If the thumb drive includes codes for multiple models ortypes of remote device, processing circuit 512 may be configured (e.g.,via software on USB device 538) to prompt the user for input regardinginformation (e.g., model of the remote device, manufacturer of theremote device, serial number of the remote device, a passkey foraccessing the information on the thumb drive, etc.).

Memory card interface 540 may be configured similarly to the USBinterface described above and vehicle control system 500 may utilizeinformation stored on memory card 542 in a fashion similar to how thevehicle control system 500 can use connected USB devices. According toyet other exemplary embodiments, memory card interface 540 maycommunicate differently with memory card 542. For example, a user mayneed to execute a program stored on memory card 542 using a filemanagement utility of processing circuit 512. According to yet otherexemplary embodiments, whenever memory card 542 is inserted into memorycard interface 540, processing circuit 512 reads memory card 542 fortransmitter configuration information (e.g., information that can beused by vehicle control system 500 so that vehicle control system 500can send authenticated transmissions to remote device 504). Memory card542 can be a flash card, a compact flash card, a SIM card, or a card ofany other type or technology. According to an exemplary embodiment,memory card 542 and memory card interface 540 are utilized and areconfigured to be utilized exclusively for receiving information thatenables authenticated communications between vehicle control system 500and remote device 504.

According to other exemplary embodiments, vehicle control system 500includes a transmitter interface 503 that is configured to allow userremoval and provision of transmitter 502. According to an exemplaryembodiment, transmitter circuit 502 for vehicle control system 500 maybe upgraded by removing the old transmitter and plugging in or otherwiseproviding/connecting transmitter 502 to the vehicle control system.According to an exemplary embodiment, processing circuit 512 isconfigured to recognize a newly plugged-in transmitter and is configuredto utilize transmitter 502 to transmit authenticated control signals toremote device 502 and/or to train vehicle control system 500 forauthenticated transmissions to remote device 504. According to yetanother exemplary embodiment, the device plugged into the vehiclecontrol system may be a circuit board (e.g., daughter board, updateboard, etc.) configured to update the vehicle control system'stransmitter, memory for the transmitter, or memory for the vehiclecontrol system. The circuit board may be removed from the interface towhich it is installed when the update is complete or the circuit boardmay remain installed in an interface of the vehicle control system.

It is important to note that many of the methods described herein can beutilized with vehicle control system 500 shown in FIG. 5. For example,many of the particular training and/or remote device actuation processesdescribed herein can be programmed into a vehicle control systemutilizing the interfaces, communications devices, and/or logic processesdescribed with reference to FIG. 5.

Referring now to FIG. 6, vehicle control system 600 is shown forutilizing information received from home network 604 to configure itselffor authenticated transmissions to remote device 608. Vehicle controlsystem 600 is shown to include transceiver 602, processing circuit 610,transmitter 606, and user interface electronics 614. Transceiver 602 maybe an IEEE 802.11 compatible transceiver, a WiMax transceiver, aBluetooth transceiver, a ZigBee transceiver, or any other transceivercompatible with wireless home networking devices. A user of home network604 may be able to download codes for communicating with remote device608 via a personal computer connected to home network 604. Vehiclecontrol system 600 and/or processing circuit 610 may be configured toreceive communications “pushed” to the transceiver 602 via a device ofhome network 604 or vehicle control system 600/processing circuit 610may be configured to allow a user to request the information from homenetwork 604 using user interface electronics 614 (e.g., buttons, a touchscreen, a keypad, a dial, a voice recognition system, etc.). Forexample, if a user purchases a new remote device 608 (e.g., a new garagedoor opener) for which vehicle control system memory 612 does notalready include codes and/or algorithms for use with remote device 608,the user can control the update process with controls in the vehicle.The user might, by way of further example, select a menu option such as“Update HomeLink®.” Upon selection of the menu option, vehicle controlsystem 600 may prompt the user to enter information regarding remotedevice 608. Using the entered information, vehicle control system 600can communicate a request for an update to home network 604 (e.g.,and/or to a device thereon). According to an exemplary embodiment, ifhome network 604 is connected to the internet, vehicle control system600 can connect to a remote server for the update via home network 604.In another embodiment, a vehicle manual may instruct a user to access awebsite with his or her home computer (e.g., http://www.homelink.com/)to request updates for vehicle control system 600 to be compatible withremote device 608. The user can download software that is installed on apersonal computer for transferring the updates to vehicle control system600. The software may request a connection to vehicle control systemtransceiver 602, which a user can accept via user interface electronics614, and transmit the update to vehicle control system 600. Processingcircuit 610 can then use the user interface electronics to ask the userwhether he or she would like to install the available vehicle controlsystem update. The update may include, for example, one or more fixedcodes, rolling codes, or other messages for transmission to remotedevice 608. Once updated, vehicle control system 600 can be trained withremote device 608 (e.g., so that remote device 608 can expect to receivea message from vehicle control system 600 including vehicle controlsystem 600's identifier, to synchronize a rolling code count, etc.). Thetraining process may or may not involve an original transmitter,depending on remote device 608 or the embodiment of vehicle controlsystem 600. According to an exemplary embodiment, as a part of theupdate from a home network or personal computer, the software installedon the personal computer can configure the vehicle control system totransmit particular codes and/or to associate particular codes, codeschemes, algorithms, or the like with particular user interface elementsin the vehicle. In some exemplary embodiments, the home network may beused to both download software (e.g., a new algorithm, a new code set)for the vehicle control system and to particularly configure the vehiclecontrol system to conduct a first transmission when a firstvehicle-mounted user interface element is actuated and to particularlyconfigure the vehicle control system to conduct a second transmissionwhen a second vehicle-mounted user interface element is actuated. Forexample, the personal-computer installed software can use a wirelesscommunications link with the vehicle control system to associate rollingcode ‘x’ with button ‘a’ and rolling code ‘y’ with button ‘b’.

Referring now to FIG. 7, a block diagram of an original transmitter 702and a vehicle control system 700 is shown, according to an exemplaryembodiment. Original transmitter 702 is shown to include a transmitter704 as well as a transceiver 706. Transmitter 704 may be a transmitterspecifically configured for authenticated transmissions to a remotedevice such as a garage door opener. According to an exemplaryembodiment, transmitter 704 is configured to transmit between afrequency range of about 285 Mhz to 450 Mhz signals. Transceiver 706 maybe configured for transmissions to and/or from systems 710-716. Whiletransceiver 706 is mentioned as having both transmit and receivefunctionality, it should be appreciated that transceiver 706 may notinclude a receiver and may only be a transmitter, according to variousalternative embodiments. Vehicle control system 700 is shown to includeprocessing circuit 718 and memory 720, which may be configured aspreviously described with reference to vehicle control system processingcircuits and/or memory devices. Transmitter 722 is configured totransmit control signals to the remote device for the purpose oftraining and/or for the purpose of normal transmissions (e.g., actuatingtransmissions, authenticated transmissions, etc.) to the remote device.According to an exemplary embodiment, vehicle control system 700includes one or more of systems/devices 710-716 and the systems/devicesand processing circuit 718 are configured to use receptions atsystems/devices 710-716 to receive and use information from transceiver706 for the purpose of configuring vehicle control system 700 forcommunications with the remote device. For example, vehicle controlsystem 700 may utilize a link with the remote keyless entry system 710to receive one or more codes for storage in memory 720 and forcommunication to a garage door opener or other remote device viatransmitter 722. Similarly, Bluetooth transceiver 712, WiFi transceiver714, and/or WiMax transceiver 716 may be configured to receiveinformation about the remote device to which vehicle control system 700will be trained from original transmitter transceiver 706.

Referring now to FIG. 8, a block diagram of vehicle control system 802is shown mounted in vehicle 800, according to an exemplary embodiment.Vehicle control system 802 is configured to transmit control signals toremote device 820 via transmitter 804. According to the exemplaryembodiment shown in FIG. 8, remote device 820 includes a training button822 (or another user interface element) for setting remote device 820into a training mode—during which remote device 820 can configure itselfto receive and authenticate control signals from a device (e.g., vehiclecontrol system 802) different than the original transmitter. Actuationof training button 822 may only cause the training mode to be enabled(e.g., during which a time window is open for receiving and processingcontrol signals for training purposes) for a short period of time (e.g.,30 seconds, 10 seconds, less than one minute, one minute, less than 2minutes, etc.). During the period of time that the training mode isenabled, the user must cause vehicle control system 802 to transmit acontrol signal to receiver 824 so it can be learned by remote device820. According to an exemplary embodiment, the user can cause vehiclecontrol system 802 to transmit a control signal to receiver 824 usingkey fob 810 which is configured with a transmitter 814 and a UI element812. According to an exemplary embodiment, one or more UI elementactivities (e.g., a series of button presses, holding a button down,pressing a small button hidden under the battery cover, pressing a smallbutton with a pen tip, etc.) can cause a circuit within key fob 810 totransmit a signal formatted for recognized reception by receiver 806 andformatted to cause vehicle control system 802 to transmit a controlsignal for receiver 824 via transmitter 804. It should be appreciatedthat transmitter 814 and receiver 806 may be configured for any type ofwireless communications (e.g., optical, radio frequency,standards-based, proprietary, Bluetooth. ZigBee, etc.).

Transmitting Different Codes in Different Windows for “Guess and Test”Type Training Systems

In some training systems that are sometimes called “guess and test” typetraining systems, the transmitter sends many different codes to thereceiver and, upon observation of a valid reception, the vehicle controlsystem stores the likely code or codes that resulted in the validreception. As new remote devices (e.g., garage door openers) arereleased with new codes, the number of codes that the transmitter usesduring a guess and test training process correspondingly increases.However, due to a number of factors including, for example, a relativelyshort training window used by various commercialized receivers,regulations regarding how long a transmitter can continuously transmit,transmitters may not be configured to transmit all of the codes storedin memory in sequence.

Referring now to FIG. 9, a flow chart of a process 900 for training a“guess and test” type vehicle control system and a receiver of a remotedevice for authenticated communications is shown, according to anexemplary embodiment. Process 900 is shown to include a user pressing abutton on a receiver to open a first learn window (step 902). Process900 further includes a user pressing and holding a button associatedwith the vehicle control system to cause a first set of codes totransmit to the remote device receiver from the vehicle control system(step 904). If the receiver does not indicate reception of a valid code,the user can press a button on the receiver to open a second learnwindow (step 906). When the user again presses and holds a buttonassociated with the vehicle control system, a second set of codes willbe transmitted to the receiver (step 908), the second set of codes beingdifferent than the first set of codes. In other words, FIG. 9illustrates a process wherein the vehicle control signal is configuredto transmit a second group of codes (e.g., sequentially, in a condensedfashion, etc.) upon a second “training” request (e.g., received by auser button press, received via touch screen, etc.). According to anexemplary embodiment, the vehicle control system may be configured tobegin a “guess and test” training process upon receiving a user commandto do so, and may train (e.g., store one or more codes in memory) whenthe user (or the remote device) provides an indication that a recentlytransmitted code resulted in an authenticated reception (e.g., thegarage door is observed to open and the user provides input stating asmuch, the remote device sends a signal indicating authenticatedreception back to the vehicle control system).

Sending Condensed Messages During a “Guess and Test” Training Procedure

Referring now to FIG. 10, a flow chart of a process 1000 is shown fortransmitting condensed messages (e.g., codes) from a vehicle controlsystem to a remote device during a “guess and test” type trainingprocedure, according to an exemplary embodiment. Process 1000 is shownto include a user pressing a button on a receiver to open a first learnwindow (step 1002). It is important to note that the learn window of thereceiver may be opened via any number of different methods (e.g., bysending an original transmitter control signal to the receiver, bypressing a button on a wall of a garage door opener, etc.). Process 1004further includes a user pressing a button associated with the vehiclecontrol system to cause a first set of codes to transmit to thereceiver, the first set of codes including the same message transmittedat multiple frequencies (step 1004). Process 1006 is further shown toinclude the user again pressing a button associated with the vehiclecontrol system to cause a second set of codes to transmit to thereceiver, the second set of codes including a next message at multiplefrequencies (step 1006).

Training a Vehicle Control System Based on User Input Received During a“Guess and Test” Type Training Procedure

Referring now to FIG. 11, a flow chart of a process 1100 is shown fortransmitting training a vehicle control system based on user inputreceived during a “guess and test” type training procedure, according toan exemplary embodiment. Process 1100 is shown to include opening afirst learn window at the receiver in response to user input (e.g., auser pressing a button) or another triggering activity (step 1102).Process 1100 is further shown to include causing a first set of codes totransmit to the receiver in response to input received at the vehiclecontrol system (step 1104). Process 1100 is shown to further includecausing a second set of codes to transmit to the receiver, the secondset of codes being different than the first set (step 1106). Process1100 is further shown to include the user indicating that the second setof codes resulted in a successful reception by the remote device byproviding user input to the vehicle control signal (step 1108). In otherwords, FIG. 11 illustrates a process whereby the user conducts an inputactivity to transmit different sets of codes and provides a differentinput activity when one of the sets of codes results in a successfulreception by the remote device. It is important to note that thesuccessful reception can be indicated by the remote device if the remotedevice includes a transmitter or a transceiver for communicating withthe vehicle control system. Regardless of how received, when the vehiclecontrol system receives an indication that the remote device hasreceived a recognized control signal, the vehicle control system willtrain itself to one or more of the recently transmitted codes. Forexample, the vehicle control system may store a pointer to thelast-transmitted code (or set of codes) for use in normal modeactivities (e.g., so that input requesting transmission to a garage dooropener results in the proper code being transmitted to the garage dooropener). According to various exemplary embodiments, this activity maybe repeated over time to narrow down to which code is actually (e.g.,probably) the valid code that causes the remote system to actuate. Forexample, the last set of codes indicated by the user to be accepted bythe remote device might include a plurality of codes (e.g., ten code). Asecond iteration of the training activity might include the first fivecodes in a first button press and the second five codes in a secondbutton press, the user provided with a mechanism to indicate which ofthe code series caused the remote device to actuate. Accordingly, thetraining process might prompt the user for two or more training “rounds”to obtain a small code set for storing in memory for regulartransmission to the remote device. In yet other exemplary embodiments,the user's behavior during regular transmissions to the remote device,over time, can be used to reduce the number of codes transmitted to theremote device. For example, the user can be instructed to hold thetransmit button down until he or she sees the remote device actuate. Ifthe user releases the button prior to the entire set of currentlytrained codes transmitting, the vehicle control system can be configuredto remove the codes after the button release from the transmission queuefor the next time the user presses the button. Further, in yet otherexemplary embodiments, the vehicle control system is configured toobserve the user's behavior by attempting to reorder the codes fortransmission and/or to attempt leaving some codes out of a transmission.For example, the vehicle control system may be configured to randomly(or otherwise) try removing codes from a transmission. If the vehiclecontrol system observes that the transmission worked without the removedcodes (e.g., if the user does not press the button again then thetransmission probably worked, if the user drives forward and parks thecar shortly after transmission then the transmission probably worked,etc.), then the vehicle control system will not transmit that codeagain. This “pruning” process can be repeated over time to result in ashort list of codes for transmission to the remote device during normaloperation—improving the observed responsiveness of the vehicle controlsystem relative to the remote device.

Sorted Codes for Transmissions During a “Guess and Test” Type TrainingProcedure

Some remote device receivers have longer “guess and test” type learningwindows than others. For example, a first “guess and test” type receivermay hold a learning window open for thirty seconds while a second “guessand test” type receiver may hold its learning window open for fortyseconds or fifty seconds. According to an exemplary embodiment, avehicle control system is configured to transmit codes in an sortedorder corresponding to learning window lengths of receivers associatedwith the stored codes.

Referring now to FIG. 12, a flow chart of a process 1200 is shown foroperating a receiver and a vehicle control system in “guess and test”type training procedure, according to an exemplary embodiment. Process1200 is shown to include opening a first learn window at the receiver(e.g., via button press at the receiver)(step 1202). Process 1200 isfurther shown to include receiving user input at a vehicle controlsystem (step 1204) and transmitting codes for older receivers prior totransmitting codes for newer receivers and/or receivers having longertraining windows (step 1206). In other words, codes for use by a vehiclecontrol system in a “guess and test” type training procedure aretransmitted to the receiver in an order at least partially based on anexpected training window at the receiver for receiving the codes.

Requesting a Longer Learning Window From a “Guess and Test” TypeReceiver

Referring now to FIG. 13, a flow chart of a process 1300 is shown forusing a vehicle control system to request a longer learning window froma “guess and test” type receiver, according to an exemplary embodiment.Process 1300 is shown to include causing a receiver to open a learnwindow (step 1302). Process 1300 is further shown to include receivinguser input at the vehicle control system to transmit codes to the remotedevice for the purpose of “guess and test” type training (step 1304).The vehicle control system will transmit codes until it receives anindication of successful training (step 1306). After transmitting anumber of codes, the vehicle control system may check for whether theindication is received during a first period of time (step 1308). If thebutton is not released, then the vehicle control system sends a signalto the receiver to request that the receiver extend the learn window(step 1310). Upon receiving the request, the receiver may open a secondlearning window or extend the first learning window. The vehicle controlsystem then continues transmitting codes until it receives theindication of successful training (step 1312), with the vehicle controlsystem training (e.g., storing one or more codes or pointers to codes)based on when the indication is received (step 1314).

Various Alternative Configurations of the Above-Described Embodiments

While the exemplary embodiments illustrated in the figures and describedherein are presently preferred, it should be understood that theembodiments are offered by way of example only. Accordingly, the presentapplication is not limited to a particular embodiment, but extends tovarious modifications that nevertheless fall within the scope of theappended claims.

The construction and arrangement of the systems as shown in the variousexemplary embodiments are illustrative only. Although only a fewembodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, orientations,etc.). For example, the position of elements may be reversed orotherwise varied and the nature or number of discrete elements orpositions may be altered or varied. Accordingly, all such modificationsare intended to be included within the scope of the present disclosure.The order or sequence of any process or method steps may be varied orre-sequenced according to alternative embodiments. Other substitutions,modifications, changes, and omissions may be made in the design,operating conditions and arrangement of the exemplary embodimentswithout departing from the scope of the present disclosure. For example,although some of the embodiments described above are described withreference to rolling code messages or signals, other embodiments may beconfigured to conduct the same activities on, with, or using fixed codemessages or a combination of rolling code messages and fixed codemessages.

Embodiments within the scope of the present disclosure include programproducts comprising machine-readable media for carrying or havingmachine-executable instructions or data structures stored thereon. Suchmachine-readable media can be any available media that can be accessedby a general purpose or special purpose computer or other machine with aprocessor. By way of example, such machine-readable media can compriseRAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to carry or store desired program code in the form ofmachine-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer or othermachine with a processor. When information is transferred or providedover a network or another communications connection (either hardwired,wireless, or a combination of hardwired or wireless) to a machine, themachine properly views the connection as a machine-readable medium.Thus, any such connection is properly termed a machine-readable medium.Combinations of the above are also included within the scope ofmachine-readable media. Machine-executable instructions include, forexample, instructions and data which cause a general purpose computer,special purpose computer, or special purpose processing machines toperform a certain function or group of functions.

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

What is claimed is:
 1. A control system for mounting in a vehicle andfor transmitting a signal to a receiver associated with a device foropening or closing a movable barrier when the receiver receives anauthorized signal, the control system comprising: an interfaceconfigured to exchangeably and physically receive differenttransmitters, the interface configured to allow for a first transmitterto be removed from the interface and a different transmitter to bephysically connected to the interface; a power supply configured tosupply power to the interface; a user input interface configured toreceive user input from a user interface element; a circuit communicablycoupling the user input interface and the interface for receiving atransmitter, the circuit configured to utilize different transmittersreceived by the interface so that common user input received at the userinput interface results in like behavior by the different transmitters.2. A control system for mounting in a vehicle and for transmitting asignal to a receiver associated with a device for opening or closing amovable barrier when the receiver receives an authorized signal, thecontrol system comprising: a transmitter; memory storing a plurality ofcodes, a first group of the codes compatible with a first set ofreceiver standards and a second group of the codes associated with asecond set of receiver standards; an input configured to receive acommand from a user interface element; a circuit configured to cause thetransmitter to transmit the first group of codes followed by the secondgroup of codes when the command is received at the input, wherein thetransmission of the first group of codes and the transmission of thesecond group of codes are both formatted to control the same receiverand associated device for opening or closing a movable barrier.
 3. Thecontrol system of claim 1, wherein the transmitter is configured totransmit a first group of codes followed by a second group of codes whenuser input is received at the user input interface, wherein the firstgroup of the codes is compatible with a first set of receiver standardsand the second group of the codes is compatible with a second set ofreceiver standards, and wherein the transmission of the first group ofcodes and the transmission of the second group of codes are bothformatted to control the same receiver and associated device for openingor closing a movable barrier.
 4. The control system of claim 1, whereinthe interface is configured to accept a circuit board, and wherein thecircuit board is configured to update the control system.
 5. The controlsystem of claim 1, wherein the control system is configured to betrained when a different transmitter is received in the interface. 6.The control system of claim 1, wherein the control system is configuredto remain trained when a different transmitter is received in theinterface.
 7. The control system of claim 1, wherein the interface is aplug-in interface configured to receive a portion of the transmitter. 8.The control system of claim 2, further comprising: an interfaceconfigured to exchangeably and physically receive differenttransmitters, the interface configured to allow for a first transmitterto be removed from the interface and a different transmitter to bephysically connected to the interface; a power supply configured tosupply power to the interface; and a circuit communicably coupling theuser interface element and the interface, the circuit configured toutilize different transmitters received by the interface so that commonuser input received at the user interface element results in likebehavior by the different transmitters.
 9. The control system of claim2, wherein the control system is configured to transmit the second groupof codes after first receiving a second command at the input.
 10. Thecontrol system of claim 2, wherein the user interface element is one ofa button, switch, touch-sensitive element, voice recognition system, ortouch screen.
 11. The control system of claim 2, wherein the first setof receiver standards includes a fixed code protocol, and wherein thesecond set of receiver standards includes a rolling code protocol.